Vehicle recommendation and translation system for setting personalized parameters within vehicles of mobility sharing environments

ABSTRACT

A system for setting parameters within a first vehicle for a first user of the first vehicle is provided and includes a memory, transceiver, and a processing module. The memory stores normalized parameters, which are specific to the first user. Each of the normalized parameters is a parameter of the vehicle. The transceiver receives the normalized parameters from a mobile device of the first user, a server in a cloud-based network, or a portable memory device. The processing module: determines whether the first user is authorized for parameter translation services; if the first user is authorized for parameter translation services, translates the normalized parameters to resultant parameters; generates parameter recommendations based on the resultant parameters; presents the parameter recommendations to the first user; and adjusts current parameters of the first vehicle based on the resultant parameters and a received response from the first user with regards to the parameter recommendations.

FIELD

The present disclosure relates to setting personalized parameters withinvehicles of mobility sharing environments.

BACKGROUND

The background description provided here is for the purpose of generallypresenting the context of the disclosure. Work of the presently namedinventors, to the extent it is described in this background section, aswell as aspects of the description that may not otherwise qualify asprior art at the time of filing, are neither expressly nor impliedlyadmitted as prior art against the present disclosure.

Automotive vehicles have traditionally been purchased and used as a mainform of transportation. There is an increasing trend away from vehicleownership. As a first alternative to purchasing a vehicle, a vehicle maybe rented by a customer from a vehicle rental company. As a secondalternative, a vehicle may be shared by multiple users via a “carsharing” service.

SUMMARY

A system for setting parameters within a first vehicle for a first userof the first vehicle is provided. The system includes a memory,transceiver, and a processing module. The memory is configured to storenormalized parameters. The normalized parameters are specific to thefirst user. Each of the normalized parameters is a parameter of thevehicle. The transceiver is configured to receive at least some of thenormalized parameters from at least one of a mobile device of the firstuser, a server in a cloud-based network, or a portable memory device.The processing module is configured to: determine whether the first useris authorized for parameter translation services; if the first user isauthorized for parameter translation services, translate the normalizedparameters to resultant parameters; generate parameter recommendationsbased on the resultant parameters; present the parameter recommendationsto the first user; and adjust current parameters of the first vehiclebased on (i) the resultant parameters, and (ii) a received response fromthe first user with regards to the parameter recommendations.

In other features, a method of setting parameters within a first vehiclefor a first user of the first vehicle is provided. The method includesstoring in one or more memories normalized parameters. The normalizedparameters are specific to the first user. Each of the normalizedparameters is a parameter of the vehicle. The method further includes:receiving at least some of the normalized parameters from at least oneof a mobile device of the first user, a server in a cloud-based networkor a portable memory device; determining whether the first user isauthorized for parameter translation services; if the first user isauthorized for parameter translation services, translating thenormalized parameters to resultant parameters; generating parameterrecommendations based on the resultant parameters; presenting theparameter recommendations to the first user; and adjusting currentparameters of the first vehicle based on (i) the resultant parameters,and (ii) a received response from the first user with regards to theparameter recommendations.

Further areas of applicability of the present disclosure will becomeapparent from the detailed description, the claims and the drawings. Thedetailed description and specific examples are intended for purposes ofillustration only and are not intended to limit the scope of thedisclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure will become more fully understood from thedetailed description and the accompanying drawings, wherein:

FIG. 1 is a functional block diagram of an example of a vehiclerecommendation and translation system in accordance with an embodimentof the present disclosure;

FIG. 2 is a functional block diagram of an example of a vehicleincluding a translation module in accordance with an embodiment of thepresent disclosure;

FIG. 3 is an example signal diagram illustrating an overview of atranslation method in accordance with an embodiment of the presentdisclosure;

FIG. 4 is a functional block diagram of an example of a portion of thetranslation module in accordance with an embodiment of the presentdisclosure;

FIG. 5 is a functional block diagram of an example of another portion ofthe translation module in accordance with an embodiment of the presentdisclosure;

FIG. 6 illustrates an example authentication method in accordance withan embodiment of the present disclosure;

FIG. 7 illustrates an example of a first portion of a personalizedparameter setting method in accordance with an embodiment of the presentdisclosure;

FIG. 8 illustrates an example of a second portion of the personalizedparameter setting method in accordance with an embodiment of the presentdisclosure; and

FIG. 9 illustrates an example of another personalized parameter settingmethod in accordance with an embodiment of the present disclosure.

In the drawings, reference numbers may be reused to identify similarand/or identical elements.

DETAILED DESCRIPTION

Each time a person rents a vehicle and/or obtains access to and drives acar sharing vehicle, the user needs to adjust settings within thevehicle. The settings include driver seat forward and backwardpositions, seat back angles, lumbar supports, mirror positions, radiostations, climate control settings, etc. This can be time consuming.Additional time may be needed when the user switches between vehicles ofdifferent years, makes, models and trim levels (collectively referred toherein as “vehicle types”). This is because the user is not accustomedto the current vehicle and may be unsure how to make certain adjustmentsand/or may be unsure as to what are the preferred settings of the userfor that particular vehicle.

Systems and methods are set forth herein that provide a seamlesspersonalized user experience across different vehicle types. Thedisclosed methods are implemented to provide a seamless experience forusers when switching vehicles and when obtaining access to vehicles fora first time. The seamless experience is also provided for a user whenobtaining access to a vehicle for a first time since another user hasobtained access to and/or driven the vehicle. In being “seamless”, afirst user is able to access and operate a vehicle for a first timesince a second user has operated the vehicle and have the feeling thatno other person used this vehicle since the last time the first userused the vehicle. Vehicle parameters are automatically adjusted afterbeing used by the second user and after authentication and providedaccess to the first user. The parameters are set to match parameterspreviously set for the first user during a previous use of the vehicleby the first user.

As another example, a first vehicle may automatically adjust vehicleparameters for a user that match vehicle parameters previously set in asecond vehicle for the user. The second vehicle may be the same vehicletype as the first vehicle. The first vehicle may be used for a firsttime by the user and after the user operated the second vehicle. Indoing so, the user may have the opinion that the first vehicle is setupthe same as the second vehicle.

As yet another example, a first vehicle may automatically adjust vehicleparameters for a user that match and/or correspond to vehicle parameterspreviously set in a second vehicle for the user. The second vehicle maybe a different vehicle type than the first vehicle. The first vehiclemay be used for a first time by the user and after the user operated thesecond vehicle. In doing so, the user may have the opinion that thefirst vehicle has been custom configured (or setup) for the user.

Other examples are described below. Some of the examples include settingparameters in a first vehicle for a first user based on parameters setin the first vehicle and/or other vehicles for other users.

The seamless experience is provided across various vehicle types (i.e.makes and/or models) and for various mobility sharing environments, suchas a family vehicle sharing environment, a car sharing environment, arental vehicle environment, etc. The systems and methods may also beapplied to other vehicles used in non-sharing mobility environments,such in individually purchased vehicles. The disclosed systems createstore and utilize user profiles that are fitted, translated and used forsetting, estimating, suggesting and predicting appropriate settings (orparameters) for current (or target) vehicles of corresponding vehicleenvironments.

FIG. 1 shows a vehicle recommendation and translation system 100 thatincludes a cloud-based network 102, a mobile device 104, and a vehicle106. The cloud-based network 102 includes one or more servers (oneserver 108 is shown). Although a single mobile device 104, a singlevehicle 106 and a single server 108 are shown, any number of each may beincluded in the vehicle recommendation and translation system 100. Theserver 108 may include a server control module 110, a memory 112, and atransceiver 114. The server control module 110 includes a translationmodule 116. The memory 112 may store databases 118 having variousinformation, such as user profiles, vehicle parameters, vehicle data,and other historical data. A user may have one or more user profiles,where each user profile includes personalized parameters set and/orselected by a user for one or more vehicle types. The content of a userprofile is further described below. The user profile may include vehicleparameters preferred by the corresponding user. The vehicle parametersmay include, for example, seat settings, radio settings, climate controlsettings, lighting settings, and/or other vehicle settings preferred andable to be set by a user. The vehicle parameters may include otherparameters, such as vehicle codes, transmission protocols, part and/orsystem dimensions, operating speeds, flow rates, etc.

The translation module 116 translates a user profile includingcorresponding parameters for a particular vehicle to other user profilesfor the same user, where the other user profiles include parameters forother vehicles. The translation may be based on user profiles of otherusers. This is further described below. The translation may be performedbased on user profile data stored in a mobile device (or network device)of a user, such as in a mobile phone, a laptop computer, a wearabledevice, and/or other network device and provided to the translationmodule 116. Although the translation module 116 is shown as beingimplemented in a cloud-based network, the translation module 116 may beimplemented in the vehicle 106. An example of a translation module beingimplemented in a vehicle is shown in FIG. 2. The translation module 116may transmit a generated user profile to, for example, the vehicle 106.The vehicle 106 may then adjust vehicle parameters based on the receiveduser profile customized for that vehicle.

The mobile device 104 may include a mobile device control module 120, amemory 122, a transceiver 124, a display 126 and an input device 128(e.g., a touch screen, a mouse, a keyboard, etc.). The memory 122 maystore user profiles 130, parameters 132, and other historical data 134.Each of the user profiles 130 may be for a particular user and aparticular vehicle and include vehicle parameters as disclosed herein.The mobile device control module 120 may store user profiles receivedfrom the control module 110 and/or from control modules of vehicles(e.g., the vehicle 106).

The vehicle 106 may include a vehicle control module 140, a memory 142,a transceiver 144, and a display 146. The memory 142 may store userprofiles 148, vehicle parameters 150 and other historical data 152. Oneor more of the user profiles 148 may match one or more of the userprofiles 130. The display 146 may be a display on a dashboard of thevehicle 106, a heads-up-display, or other display within the vehicle106. The control modules 110, 120, 140 may communicate with each othervia the transceivers 114, 124, 144.

The databases 118 may include a user profile database, which stores userprofiles including preferences of users for various vehicles. The dataof the user profiles are analyzed by the translation module 116 toextract relationships between vehicle types when users switch vehicles.This may be based on data collected from a controller area network ofone or more vehicles as described below, such as: seat angles;temperatures; mathematical model data from mathematical models; data asa result of calculations; data associated with adjustments; and otherdata examples of which are disclosed herein. Recommended user profilesare generated and one or more sets of user profile mapping informationmay be generated for translation purposes. The sets of user profilemapping information may be used to translate a current user profile (orcurrent user parameters/preferences) for one or more previous vehiclesto a new user profile for a current vehicle. Individual user parametersmay be compared and similarities between users and/or user parametersmay be stored. Accordingly, when a user drives a new vehicle, a new setof settings are offered for the user to accept and/or modify.

The examples set forth herein are applicable to (i) multiple personalvehicles, such as that used in a mobility sharing environment, and (ii)various user settings. The user preference parameters may be saved in auser's personal device (e.g., the mobile device 104) and/or in thecloud-based network 102. The translation module 116 provides recommendedparameters based on similar attributes and translates parameterspreviously set for a first vehicle to parameters for a second vehicle ofthe same or different type. The system 102 is not dependent onconnections between user devices and accounts for physical properties ofthe attributes to be applied (e.g., seat dimensions, heating ventilationand air-conditioning (HVAC) capabilities, etc.). The parameters areadapted from one vehicle to another vehicle that may have heterogeneousattributes based on build, model, etc. The translation module 116 isable to generalize to unseen environments and incorporates machinelearning techniques for user profiles to recommend and translateparameters.

FIG. 2 shows a vehicle 200 that may include an operating system 202. Thevehicle 200 may replace and/or operate similarly to the vehicle 106 ofFIG. 1. The operating system 202 may include a vehicle control module204, a translation module 206, and other control modules 208, which maycommunicate with each other via a controller area network (CAN) bus 210.Although the examples disclosed herein are primarily described withrespect to communication over a network including one or more CAN buses,the examples may be applied to and/or include other in-vehicle networkssuch as Flexray™, automotive Ethernet, etc. The translation module 206may operate similarly to the translation module 116 of FIG. 1. Thevehicle control module 204 may operate similar to the vehicle controlmodule 140 of FIG. 1 and includes an authorization module 211, aparameter adjustment module 212, and/or other modules, such as anautonomous control module, engine control module, a transmission controlmodule, and a motor control module, etc. The authorization module 211may control access to an interior of the vehicle 200 and access to userprofile translation services, as described further below. The parameteradjustment module 212 may be used to adjust parameters of the vehicle200.

The operating system 202 may further include a transceiver 213, sensors214, a navigation system 216, a memory 218, a display 220 and an audiosystem 222. The sensors 214 may include cameras, objection detectionsensors, temperature sensors, and/or other sensors that provideparameters and/or data associated with the state of the vehicle 200,state of objects within the vehicle, and/or information regarding anenvironment in which the vehicle 200 is located. The sensors 214 detectenvironmental conditions and status of vehicle devices. The navigationsystem 216 may include a global positioning system (GPS) receiver 224.

The memory 218 may store sensor data and/or parameters 230, userprofiles 232, tables 234 with codes and corresponding parameter values(or parameters), other historical data 236, and applications 238. Theapplications 238 may include applications executed by the modules 204,206, 208. As an example, one of the applications may be a translationapplication executed by the translation module 206 and used to convert(or translate) user profiles and/or corresponding parameters.

The vehicle control module 204 may control operation of an engine 240, aconverter/generator 242, a transmission 244, a window/door system 250, alighting system 252, a seating system 254, a mirror system 256, a brakesystem 258, electric motors 260 and/or a steering system 262 accordingto parameters set by the modules 204, 206, 208. The vehicle controlmodule 204 may receive power from a power source 264 which may beprovided to the engine 240, the converter/generator 242, thetransmission 244, the window/door system 250, the lighting system 252,the seating system 254, the mirror system 256, the brake system 258, theelectric motors 260 and/or the steering system 262, etc.

The translation module 206 may generate output signals includingparameter settings via the display 220. The translation module 206 maycommunicate with and/or receive user profile data from one or moremobile devices (e.g., the mobile device 104 of FIG. 1), cloud-basednetwork servers (e.g., the cloud-based network server 108 of FIG. 1)and/or other vehicles via the transceiver 213.

The engine 240, the converter/generator 242, the transmission 244, thewindow/door system 250, the lighting system 252, the seating system 254,the mirror system 256, the brake system 258, the electric motors 260and/or the steering system 262 may include actuators controlled by thevehicle control modules 204 to, for example, adjust fuel, spark, airflow, throttle position, pedal position, door locks, window position,seat angles, lumbar support positions and/or pressures, mirror position,stereo presets, etc. This control may be based on the outputs of thesensors 214, the navigation system 216, and the GPS 224. The statedcontrol may also be performed to match parameters of a user profile,which may be adjusted by a user. The audio system 222 may include astereo having channel presets and volume settings that maybe set by auser and adjusted according to a user profile by one or more of themodules 204, 206, 208.

A user profile may include various vehicle parameters set for aparticular user. The vehicle parameters may include set parameters,mirror parameters, window parameters, door parameters, lightingparameters, vehicle-to-infrastructure (V2X) parameters, driverassistance and safety parameters, driving parameters, infotainmentparameters, security parameters, dashboard parameters, etc. For example,seat parameters may include: seat positions; heights; seat back and seatpan inclination angles; lumbar support positions; pressures; and/orstates; and head restraint positions. Mirror parameters may include rearand side view mirror positions and/or tinting values. Window parametersmay include: adaptive tint values; moon roof positions, which may beweather dependent; and passenger window control setting values.

Door parameters may include door locking and unlocking policies, forexample, unlock all doors or just a driver door when an unlock button isdepressed once or when access to the vehicle is granted. For example,when the method of FIG. 6 is performed and access is granted a driverdoor or all doors may be unlocked depending on the unlocking policystored.

Lighting parameters may include a value indicating whether fog lightsare ON or OFF, a headlight inclination (e.g., high or low) angle, awide/narrow lighting angle, and intensity levels. Different lightingparameters may be used for different weather conditions, time of day,and/or geographical region of the vehicle. Different light parametersmay be used based on whether other vehicles or pedestrians are within apredetermined range of the host vehicle for which the parameters arebeing adjusted.

V2X parameters may include protocol preferences for sharing informationand applications permitted to interact with other vehicles and/orinfrastructure. Driver assistance and safety parameters may include: avalue indicating whether radar sensing is ON or OFF; a radarsensitivity; a radar display setting; a value indicating whether lanekeeping warning and/or assistance system is ON or OFF; a lane keepingwarning and/or assistance sensitivity; a value indicating whether aforward collision warning and/or collision mitigation system is ON orOFF; cruise control parameters, such as an automatic distance keepingparameter and semi-automatic driving and preference values; cameraassistance system parameters; automatic parking system parameters; etc.

Driving parameters may include preferred transmission settings (e.g.,sports, manual, eco, shifting points, et.) and suspension parameters.Infotainment parameters may include paired phone settings, phone bookand reading of messages settings, a policy for transferring applicationprofiles, stereo settings, etc. Security parameters may include alarmsettings including alarm sensitivity settings. Dashboard parameters mayinclude color settings; intensities; permitted application screens(e.g., navigation screens; safety notice screens; augmented maps ofsurroundings using radar systems; and camera view screens); fueleconomy, miles-per-gallon and corresponding feedback parameters; andelectric/hybrid vehicle status, battery status, regenerative brakingstatus, and visuals.

During operation, a user obtains access to and enters the vehicle 200and the vehicle 200 is configured based on previous user parameters (orsettings) and/or based on recommendations and/or suggestions. Therecommendations and/or suggestions may be determined by the translationmodule 206 based on average and/or popular settings selected by similarusers (e.g., users having similar demographic data). The userdemographic data may include user age, weight, height, gender, musicpreferences, living area, occupation, marital/family status, educationlevel, ethnic background, etc., and other demographic data such asgeographical region of vehicle. The current user may make finaladjustments to at least some of the parameters, which may already beclose to preference values of the user. The parameters may be saved inthe memory 218, sent to the server 108 of FIG. 1 and saved in the memory112, and/or saved in the memory 122 of the mobile device 104. Theoperating system 202 uses the saved settings to build a user profile andupdate one or more recommended user profiles for similar vehicles and/orfor similar users.

Use Case—Vehicle Shared Among Multiple Users

The vehicle 200 may be shared among multiple people such as: familymembers, a group of friends, employees of a company, etc. As an example,each of the users may have used the vehicle 200 at least once and hasselected and saved his/her preferred parameters/settings. User A usesthe vehicle 200 with his/her own settings. After user A is done usingthe vehicle 200, then user B uses the vehicle 200. As soon as user Benters the vehicle 200, the previous parameters/settings for user B areapplied and as far as user B is concerned, no one else has used thevehicle 200 since the last time user B used the vehicle 200. Theparameters/settings have been adjusted to be the same as the last timeuser B used the vehicle 200.

Use Case—Other Vehicles of Same Type

A user has used a first vehicle of the same type as that of the vehicle200. The user selected and saved his/her preferred parameters/settingsfor the first vehicle. The user enters the vehicle 200, the previousparameters/settings saved for the first vehicle are set on the vehicle200 and the vehicle 200 is indistinguishable from the point of the userfrom the first vehicle since the parameters/settings are the same,thereby providing a seamless experience.

New Vehicle Type

A user has used other vehicles before, but not a vehicle of the type ofthe vehicle 200. The user enters the vehicle 200 and the vehicle isconfigured using recommendations based on his/her parameters/settings inthe other vehicles and recommendations corresponding to similar usersfor vehicles of the type of the vehicle 200. The current user may makeminimal adjustments since the recommended settings are close to her/hispreferences. The recommendations may be determined by the translationmodule 206.

FIG. 3 shows an overview of a translation method. In the exampletranslation method illustrated, the translation module may be located ina server 300 of a cloud-based network (hereinafter the “network”) or ina vehicle. A memory of the network or the vehicle may store a normalizeduser profile based on previous users of the vehicle as a baseline.Normalized user profile may refer to a profile that includes parametersthat have been normalized (converted to values within a predeterminedrange, such as values between 0 and 1 or values between −1 and 1) foreasy application to any vehicle type. A baseline or updated user profilemay be calculated and stored each time a user operates the vehicle. Inone embodiment, the user profile is created in the network and thendownloaded to one or more modules 302 of the vehicle, as represented byarrow 304. In another embodiment, the user profile is created in thevehicle and then uploaded to the network to form an aggregate andnormalized user configuration for the vehicle in the network, asrepresented by arrow 306.

A user may be authenticated and authorized to access and operate thevehicle and utilize translation services based on credential informationprovided to and/or stored in the vehicle, a mobile device 308 and/orother authentication device 309 of the user. This information may beprovided to the vehicle modules 302 directly or indirectly from themobile device and/or the authentication device 309, as represented byarrows 310. The mobile device 308 may be a mobile phone, laptopcomputer, wearable device or other mobile device and communicate via,for example wireless fidelity (WiFi), long-term evolution (LTE) or otherwireless local area network communication protocols. Examples of theauthentication device 309 include a smart identification card, nearfield communication (NFC) card, a radio frequency identification (RFID)device, a smart key, a key fob, a fingerprint detection device includinga fingerprint sensor, a face recognition device including a camera, avoice recognition device including a microphone, and/or otherauthentication device. The authentication device 309 may be incorporatedin, connected to, or separate from and communicate with the mobiledevice 308 and/or the vehicle. The authentication device 309 may alsocommunicate with the server.

The mobile device 308 may provide customization parameters compatiblewith a service available in the mobile device 308 to the modules 302 ofthe vehicle as represented by arrow 314. The customization parametersare the preferences of the user. These preferences can be updated in thevehicle and then later downloaded to the mobile device 308. Thepreferences may be transmitted between the mobile device and the vehicledirectly or indirectly via the network. This may be via a gateway devicelocated internal to or external to the vehicle. Similarly, thenormalized user profile for that particular vehicle type may be obtainedfrom the network if it does not already exist in the vehicle, asrepresented by arrow 316. This may include downloading preferences fromthe server 108 of FIG. 1 if not already stored in the vehicle.

The translation module may translate the user preferences for thevehicle as represented by arrow 318. The translation module maydetermine recommendations for the user based on the preferences of theuser and/or preferences of other users and present the recommendationsto the user via, for example, a display in the vehicle or a display ofthe mobile device. This is represented by arrow 320. The recommendationsmay be generated based on similarity score computations comparingsimilarities between users, preferences, user profiles, and vehicletypes using, for example, machine learning algorithms. The user mayadjust the recommended settings, which may be done via, for example, (i)the authentication device 309 as shown and represented by arrow 322,(ii) the mobile device 308, or (iii) the vehicle. The recommendationsaccepted by the current user are stored as part of correspondingprofiles for that user. The recommendations may be stored in the networkas represented by arrow 324, in the mobile device 308 as represented byarrow 326, and/or in the vehicle. The settings may be applied to thevehicle as controller area network (CAN) messages utilizing an openapplication programming interface (API) architecture based on methodsdescribed further below.

FIG. 4 shows an example of a portion of a translation module 400, suchas the translation module 116 of FIG. 1 or the translation module 206 ofFIG. 2. The translation module 400 includes a processing module 401, amemory 402, a similarity scoring module 404, a first mapping module 406and a second mapping module 408. The memory 402 may store a personalizedrecommendation database 410, a user preference database 412, and amappings database 414.

The processing module 401 may include the parameter adjustment module212 of FIG. 2 and may receive, for example, user preferences (orprofiles), vehicle type data and environmental data from bile devices,vehicles, cloud servers, and/or other network devices. The environmentaldata may include an ambient temperature, a time of day, trafficconditions and a purpose of a trip. The processing module 401 may outputprevious user preferences (or profiles), mapped preferences (orprofiles) recommendations and/or suggestions. Recommendations may beprovided as a result of computations using machine learning. Suggestionsmay refer to general rules. The processing module 401 receives thecurrent vehicle type that user is using or about to be used. Ifapplicable, the processing module 401 also receives current parametersset for and/or by the current user. If the user is about to operate avehicle of a particular type, the previous preferences (if applicable)and recommendations are returned, applied and/or displayed. If the useralready used the vehicle of the particular type, meaning the preferenceswere already set and applied on the vehicle, then the preferences may bestored and/or analyzed for future recommendations.

The similarity scoring module 404 automatically organizes user profilesinto categories/groups based on the corresponding preferences, settings,demographics, and/or other grouping information. The first mappingmodule 406, based on the user preferences, maps parameters from avehicle model A to a vehicle model B of a same or different type asvehicle A. The second mapping module 408, based on rules, mapspreferences between vehicles of different types using mathematicalderivations and calculations and/or manually inserted relationships. Thepersonalized recommendation database 410 stores personalizedrecommendations based on assigned user categories and data in themappings database 414.

The user preference database 412 stores the preferences selected by eachuser. The mapping database 414 stores possible mappings between userprofiles for vehicles of the same or different types.

FIG. 5 shows another portion of the translation module 400 of FIG. 4.The portion includes the processing module 401 and the memory 402. Thememory 402 may store CAN APIs 500. The processing module 401 may includea settings module 502, a filter module 504 and a recommendation module506. The processing module 401 may be in communication with the vehiclecontrol module 204 and/or other control modules 208 via the CAN bus 252.The translation module 400 may be connected to the memory 218, aportable memory device 507, the transceiver 213 and the display 214. Theportable memory device 507 may include a plug-in memory card, a flashdrive, or other portable memory device. The settings module 502 maydetermine, set, and/or update user preferences. The filter module 504determines which codes are in CAN frames received via a CAN bus 252, asdescribed below. The recommendation module 506 generates recommendationsas described herein.

The systems disclosed herein may be operated using numerous methods,example methods are illustrated in FIGS. 3 and 6-9. In FIG. 6, anauthentication method is shown. Although the methods are shown asseparate methods, one or more of the methods and/or operations fromseparate methods may be combined and performed as a single method. Forexample, the methods of FIGS. 6-8 may be performed as a single method.Although FIGS. 6-8 are primarily described with respect to a translationmodule being located within a vehicle, the translation module may belocated in a server of a cloud-based network as described above and theappropriate signals may be transmitted between the server and thevehicle in order to perform at least some of the operations of FIGS.6-8. Although the following operations are primarily described withrespect to the implementations of FIG. 6, the operations may be easilymodified to apply to other implementations of the present disclosure.The operations may be iteratively performed. The method may begin at600. At 602, a user approaches a vehicle to be accessed and operated.The user has a mobile device, such as one of the mobile devices referredto herein. The vehicle control module 204 receives an authenticationinput request from a touch pad on an exterior of the vehicle, the mobiledevice, or other network device.

At 604, the authorization module 211 determines whether the user isauthorized to access an interior of the vehicle and/or to operate thevehicle. This may include comparing a digital key, password and/orsignature received in the authentication input request with apredetermined digital key, password and/or signature. If there is amatch, then the user is authorized and operation 606 is performed. Ifthe user is not authorized, the method may end at 610.

At 606, the authorization module 211 permits access to the interior ofthe vehicle by, for example, unlocking the doors of the vehicle. At 608,the translation module 400 may determine whether the user is authorizedfor preference (or translation) services as described herein. This maybe based on the same digital key, password and/or signature received at602 or based on a different digital key, password and/or signature. Inone embodiment, operations 604 and 608 are combined as a singleoperation allowing a user to be authorized during a single operation. Ifthe user is authorized for preference services, then operation 700 ofFIG. 7 may be performed, otherwise operation 610 may be performed.

FIG. 7 shows a first portion of a personalized parameter setting method.Although the following operations are primarily described with respectto the implementations of FIG. 7, the operations may be easily modifiedto apply to other implementations of the present disclosure. Theoperations may be iteratively performed. The method may begin at 700 atwhich the translation module 400 may receive access to history dataincluding user profile data received from the mobile device, a server ina cloud-based network, other vehicles and/or memory 218. This data maybe downloaded to the vehicle when the user is authorized for preferenceservices.

At 702, the processing module 401 may determine whether this is a firsttime the user is in the current vehicle type (e.g., year, make, modeland/or trim level). If yes, operation 800 of FIG. 8 may be performed,otherwise operation 704 is performed.

At 704, the processing module 401 receives a user input indicatingwhether the user has agreed to have previous parameters/preferencesettings applied. This may be based on a display of the previousparameters/preference settings on the display 214 and/or a signalsgenerated signal requesting the same. The input may be received, forexample, via the display 214, the mobile device, or other input device.At 706, if the user has agreed to have previous parameters/preferencesettings applied, then operation 708 is performed, otherwise operation710 is performed.

At 708, the settings module 502 applies the previousparameters/preference settings by setting values, temperatures,channels, seat positons, lighting, and/or other parameters as disclosedherein. At 710, the settings module 502 receives another input from theuser. This may be an indication of whether the user has requested anadjustment of one or more of the previous parameters/preferencesettings. At 712, the processing module 401 and/or the settings module502 proceeds to operation 800 of FIG. 8 if the user has requested anadjustment or to operation 714 if no adjustment has been requested.

At 714, the vehicle control module 204 may permit the vehicle to bedriven. This may occur in response to an indication signal from theprocessing module 401 indicating that the user is finished selecting andthe processing module has finished setting the parameters.

The following operations 716, 718, 720 may be performed subsequent toperforming, for example, operation 824 of FIG. 8. At 716, the settingsmodule 502 determines whether the current parameters/preference settingsare acceptable to the user. This may be based on an input received fromthe user via one of the input devices. If yes, operation 718 isperformed, otherwise operation 720 is performed.

At 718, the settings module 502 determines whether the user hasrequested to have one or more current parameters/preference settingssaved for future use. If yes, operation 720 may be performed, otherwisethe method may end at 722. At 720, the settings module 502 saves thecurrent parameters/preference settings in, for example, the memory 218.The method may end at 722 subsequent to operation 720.

FIG. 8 shows a second portion of the personalized parameter settingmethod. Although the following operations are primarily described withrespect to the implementations of FIG. 8, the operations may be easilymodified to apply to other implementations of the present disclosure.The operations may be iteratively performed. The method may begin at 800at which the processing module 401 may determine whether this is a firsttime a translation is being performed for the vehicle. If this is afirst time, operation 802 is performed, otherwise operation 806 isperformed.

At 802, the filter module 504 may read CAN frames from the CAN bus 210and/or available vehicle codes and current status values from the memory218. The filter module 504 may store codes possibly used by the vehicle(depending on the year, make, model, trim level, etc.) and detect whichof these codes are being used. The CAN frames may include control codesthat are available (i.e. being used and may be adjusted). For example,the vehicle may have particular codes for seat angles, lumbar pressures,passenger temperatures, driver temperatures, fan speeds, steering wheeltemperature, radio channels, radio volumes, and other parameters andcorresponding status values.

Operations 802, 804 may be performed while operations 806, 808, 810, and812 are performed. At 804, the filter module 504 filters the CAN framesto obtain the available vehicle codes and current status values. Thisinformation may be provided to the settings module 502 and/or therecommendation module 506. Operation 820 may be performed subsequent toperforming operation 804.

At 806, the settings module 502 determines whether the user hasrequested a new suggestion. This may be based on another received userinput. If the user has requested a new suggestion, operation 808 isperformed, otherwise operation 816 may be performed.

At 808, the settings module 502 collects current userparameters/preference settings and/or other user parameters/preferencesettings from the memory 218, a cloud-based network database, the mobiledevice, other network device. This may include receiving normalizedparameters/preference settings from the mobile device, server, or otherdevice, such as a plug-in memory card. The other device may be pluggedinto an accessory port, such as a memory card or flash drive port (e.g.,universal serial bus (USB) port) in the vehicle. An example of the otherdevice is the portable memory device 507 of FIG. 5.

At 810, the recommendation module 506 determines a recommended userprofile for the user and the vehicle. This is based on theparameters/preference settings collected at 808 and/or other aggregateduser profile data, average data, and/or data applicable to the user andthe vehicle. This may include some of the operations of the method ofFIG. 9. At 812, the recommended user profile is displayed for the user.

At 814, the recommendation module 506 determines whether a user inputhas been received selecting the recommended user profile. If the userselects the recommended user profile, then operation 816 is performed,otherwise operation 820 is performed. At 816, the settings module 502determines whether a user input has been received to change aparameter/preference setting. If yes, operation 818 is performed,otherwise operation 820 is performed. At 818, the recommended userprofile is changed based on the user changes at 816.

At 820, the settings module translates the parameters/preferencesettings for the current vehicle if needed to provide resultingparameters/preference settings. This may be based on the collectedpreferences of the user and/or other users and/or the recommended userprofile. The codes of one or more previously operated vehicles may betranslated to the codes of the current vehicle and the status values ofthe codes for the previously operated vehicles may be weighted, averagedand/or adjusted to provide the settings for the codes of the currentvehicle. The status values for the previously operated vehicles may beadjusted based on differences between, for example, vehicle dimensions,part sizes, demographics of operators/users, etc. to better correspondto the current vehicle and current user. This is done to provide aparameter set for the current vehicle and user that is essentiallyequivalent to one or more parameter sets for: the user and a vehicle ofthe same type as the current vehicle; one or more other users and/or oneor more other vehicles of the same type as the current vehicle; and/orthe user and/or one or more other users of other vehicles of differenttypes than the current vehicle. The equivalent parameter set(s) providea seamless experience for the current user. Operation 820 may includesome of the operations of the method of FIG. 9.

At 822, the processing module 401 may open (or execute) and/or initiateopening (or executing) one or more CAN APIs corresponding to theresulting parameters/preference settings to be applied. The CAN APIs mayapply at least some of the resulting parameters/preference settings. Theresulting parameters/preference settings may include identifiers, codesand corresponding values to be set. At 824, the processing module 401may store the parameters/preference settings to be applied in the memory218. This may include uploading the parameters/preference settings to beapplied to the server and/or downloading the parameters/preferencesettings to be applied to the mobile device. Operation 716 of FIG. 7 maybe performed subsequent to operation 824.

FIG. 9 shows another personalized parameter setting method. Although thefollowing operations are primarily described with respect to theimplementations of FIG. 9, the operations may be easily modified toapply to other implementations of the present disclosure. The operationsmay be iteratively performed. The method may begin at 900. At 902, thesettings module 502 may query databases (e.g., the databases 410, 412for current user settings. This may include receiving normalizedparameters/preference settings from the mobile device or server.

At 904, the processing module 401 determines whether this is a firsttime user of the translation services. If this is a first time user,then operation 906 is performed, otherwise operation 908 is performed.

At 906, the settings module 502 may apply average settings based onother user profiles for the current vehicle. As an example, the averagesettings may be determined by calculating one or more probabilitiesaccording to equation 1, where P is a probability value, X refers to oneor more parameters, i identifies the current user, U is the variable setto i, m is the current type of vehicle, M is the variable set to m, j isan integer, N is a number of user profiles, and n is an integer.

$\begin{matrix}{{P( {{{X❘U} = i},{M = m}} )} = {\frac{1}{N}{\sum\limits_{j}{P( {{{X❘U} = j},{M = n}} )}}}} & (1)\end{matrix}$

As an example, X may refer to any number of parameters and may includecontinuous correlated values c1, c2, c3 . . . and/or discontinuous (ordiscrete) values d1, d2, d3 . . . . One or more of the continuouscorrelated values and/or one or more of the discrete values may beindependent of the type of vehicle. The continuous correlated values mayhave an infinite number of settings. The discrete values may have apredetermined number of settings. For example, a discrete value mayindicate (i) ON or OFF settings, or (ii) HIGH, LOW, OFF settings.Operation 914 may be performed subsequent to operation 906.

At 908, the processing module 401 determines whether this is a firsttime that the user has operated the vehicle and a vehicle of this type.If yes, operation 910 is performed, otherwise operation 912 isperformed.

At 910, the settings module 502 applies translated settings based oncurrent user eye-point position from other vehicles. This may includeproviding recommendations as described above and then applying aselected recommendation and/or a portion thereof. The recommendationsmay be based on (i) preferences of the current user that were previouslyapplied in other vehicles, and/or (ii) preferences of other users forthis vehicle. The preferences of the current user that were previouslyused in other vehicles (i) may be independent of whether the othervehicles are similar to the current vehicle, or (ii) may only be forother vehicles similar to the current vehicle. As an example, atranslation may be performed using equation 2.P(X|U=i,M=m)=f(P(X|U=i,M=n))  (2)

At 912, if the current user has been in this vehicle type before, theuser is provided with an option to apply the previous preferences of thecurrent user or to adjust the previous preferences. The adjustments maybe performed at 914.

At 914, parameters/preference settings may be adjusted by the user andapplied by the settings module 502. If applied settings are not foundacceptable to the user, then the user may adjust the parameters. If theparameters/preference settings are not acceptable to the user, then theuser adjusts the settings (optionally with new suggestions) until theparameters/preference settings are found acceptable to the user. Whenparameters are set as desired by the user, then the user may bepermitted to drive the vehicle. The user may provide an input indicatingthat the parameters/preference settings are acceptable. Based on thepreferences of the current user, some parameters/preference settings mayautomatically be applied or the settings module 502 may request approvalfrom the user prior to enabling them.

Operations 916 and 918 may be performed subsequent to operation 914. At916, the current parameters/preference settings may be optionallywritten to the memory 218 and/or be sent to the server, the mobiledevice and/or one or more other vehicles. The parameters/preferencesettings are saved for future use.

Some of the parameters/preference settings may be restricted due tovehicle owner/provider policies and/or regional restrictions and/orregulations. This means that some of the parameters/preference settingsmay be performed for use in the current vehicle and for the current userand while in a certain geographical region, but may not be permitted orlimited in use for one or more other vehicles, users and/or othergeographical regions.

At 918, the processing module 401 may update a translation functionbased on the currently selected and set preferences. The method may endat 920 subsequent to operations 916, 918.

The above-described operations of FIGS. 6-9 are meant to be illustrativeexamples. The operations may be performed sequentially, synchronously,simultaneously, continuously, during overlapping time periods or in adifferent order depending upon the application. Also, any of theoperations may not be performed or skipped depending on theimplementation and/or sequence of events.

The foregoing description is merely illustrative in nature and is in noway intended to limit the disclosure, its application, or uses. Thebroad teachings of the disclosure can be implemented in a variety offorms. Therefore, while this disclosure includes particular examples,the true scope of the disclosure should not be so limited since othermodifications will become apparent upon a study of the drawings, thespecification, and the following claims. It should be understood thatone or more steps within a method may be executed in different order (orconcurrently) without altering the principles of the present disclosure.Further, although each of the embodiments is described above as havingcertain features, any one or more of those features described withrespect to any embodiment of the disclosure can be implemented in and/orcombined with features of any of the other embodiments, even if thatcombination is not explicitly described. In other words, the describedembodiments are not mutually exclusive, and permutations of one or moreembodiments with one another remain within the scope of this disclosure.

Spatial and functional relationships between elements (for example,between modules, circuit elements, semiconductor layers, etc.) aredescribed using various terms, including “connected,” “engaged,”“coupled,” “adjacent,” “next to,” “on top of,” “above,” “below,” and“disposed.” Unless explicitly described as being “direct,” when arelationship between first and second elements is described in the abovedisclosure, that relationship can be a direct relationship where noother intervening elements are present between the first and secondelements, but can also be an indirect relationship where one or moreintervening elements are present (either spatially or functionally)between the first and second elements. As used herein, the phrase atleast one of A, B, and C should be construed to mean a logical (A OR BOR C), using a non-exclusive logical OR, and should not be construed tomean “at least one of A, at least one of B, and at least one of C.”

In the figures, the direction of an arrow, as indicated by thearrowhead, generally demonstrates the flow of information (such as dataor instructions) that is of interest to the illustration. For example,when element A and element B exchange a variety of information butinformation transmitted from element A to element B is relevant to theillustration, the arrow may point from element A to element B. Thisunidirectional arrow does not imply that no other information istransmitted from element B to element A. Further, for information sentfrom element A to element B, element B may send requests for, or receiptacknowledgements of, the information to element A.

In this application, including the definitions below, the term “module”or the term “controller” may be replaced with the term “circuit.” Theterm “module” may refer to, be part of, or include: an ApplicationSpecific Integrated Circuit (ASIC); a digital, analog, or mixedanalog/digital discrete circuit; a digital, analog, or mixedanalog/digital integrated circuit; a combinational logic circuit; afield programmable gate array (FPGA); a processor circuit (shared,dedicated, or group) that executes code; a memory circuit (shared,dedicated, or group) that stores code executed by the processor circuit;other suitable hardware components that provide the describedfunctionality; or a combination of some or all of the above, such as ina system-on-chip.

The module may include one or more interface circuits. In some examples,the interface circuits may include wired or wireless interfaces that areconnected to a local area network (LAN), the Internet, a wide areanetwork (WAN), or combinations thereof. The functionality of any givenmodule of the present disclosure may be distributed among multiplemodules that are connected via interface circuits. For example, multiplemodules may allow load balancing. In a further example, a server (alsoknown as remote, or cloud) module may accomplish some functionality onbehalf of a client module.

The term code, as used above, may include software, firmware, and/ormicrocode, and may refer to programs, routines, functions, classes, datastructures, and/or objects. The term shared processor circuitencompasses a single processor circuit that executes some or all codefrom multiple modules. The term group processor circuit encompasses aprocessor circuit that, in combination with additional processorcircuits, executes some or all code from one or more modules. Referencesto multiple processor circuits encompass multiple processor circuits ondiscrete dies, multiple processor circuits on a single die, multiplecores of a single processor circuit, multiple threads of a singleprocessor circuit, or a combination of the above. The term shared memorycircuit encompasses a single memory circuit that stores some or all codefrom multiple modules. The term group memory circuit encompasses amemory circuit that, in combination with additional memories, storessome or all code from one or more modules.

The term memory circuit is a subset of the term computer-readablemedium. The term computer-readable medium, as used herein, does notencompass transitory electrical or electromagnetic signals propagatingthrough a medium (such as on a carrier wave); the term computer-readablemedium may therefore be considered tangible and non-transitory.Non-limiting examples of a non-transitory, tangible computer-readablemedium are nonvolatile memory circuits (such as a flash memory circuit,an erasable programmable read-only memory circuit, or a mask read-onlymemory circuit), volatile memory circuits (such as a static randomaccess memory circuit or a dynamic random access memory circuit),magnetic storage media (such as an analog or digital magnetic tape or ahard disk drive), and optical storage media (such as a CD, a DVD, or aBlu-ray Disc).

The apparatuses and methods described in this application may bepartially or fully implemented by a special purpose computer created byconfiguring a general purpose computer to execute one or more particularfunctions embodied in computer programs. The functional blocks,flowchart components, and other elements described above serve assoftware specifications, which can be translated into the computerprograms by the routine work of a skilled technician or programmer.

The computer programs include processor-executable instructions that arestored on at least one non-transitory, tangible computer-readablemedium. The computer programs may also include or rely on stored data.The computer programs may encompass a basic input/output system (BIOS)that interacts with hardware of the special purpose computer, devicedrivers that interact with particular devices of the special purposecomputer, one or more operating systems, user applications, backgroundservices, background applications, etc.

The computer programs may include: (i) descriptive text to be parsed,such as HTML (hypertext markup language), XML (extensible markuplanguage), or JSON (JavaScript Object Notation) (ii) assembly code,(iii) object code generated from source code by a compiler, (iv) sourcecode for execution by an interpreter, (v) source code for compilationand execution by a just-in-time compiler, etc. As examples only, sourcecode may be written using syntax from languages including C, C++, C #,Objective-C, Swift, Haskell, Go, SQL, R, Lisp, Java®, Fortran, Perl,Pascal, Curl, OCaml, Javascript®, HTML5 (Hypertext Markup Language 5threvision), Ada, ASP (Active Server Pages), PHP (PHP: HypertextPreprocessor), Scala, Eiffel, Smalltalk, Erlang, Ruby, Flash®, VisualBasic®, Lua, MATLAB, SIMULINK, and Python®.

None of the elements recited in the claims are intended to be ameans-plus-function element within the meaning of 35 U.S.C. § 112(f)unless an element is expressly recited using the phrase “means for,” orin the case of a method claim using the phrases “operation for” or “stepfor.”

What is claimed is:
 1. A system for setting parameters within a firstvehicle for a first user of the first vehicle, the system comprising: amemory configured to store a plurality of normalized parameters, whereinnormalized parameters refer to parameters that have been converted tovalues within a predetermined range for application to a plurality ofdifferent vehicle types, wherein the plurality of normalized parametersare specific to the first user, and wherein each of the plurality ofnormalized parameters is a parameter of the first vehicle; a transceiverconfigured to receive at least some of the plurality of normalizedparameters from at least one of a mobile device of the first user, aserver in a cloud-based network, or a portable memory device; and aprocessing module configured to determine, based on credentialinformation, (i) whether the first user is authenticated and authorizedto access and operate the first vehicle, and (ii) whether the first useris authorized to utilize parameter translation services, the processingmodule is configured to determine whether the first user is authorizedto utilize parameter translation services separate from determiningwhether the first user is authenticated and authorized to access andoperate the first vehicle, based on the first user being authenticatedand authorized to access and operate the first vehicle, permittingaccess to an interior of the first vehicle, based on the first userbeing authorized for the parameter translation services, translate theplurality of normalized parameters to resultant parameters based on aprofile of parameters of the first vehicle or a second vehicle, and theprofile of parameters is specific to a second user, generate parameterrecommendations based on the resultant parameters, present the parameterrecommendations to the first user, and adjust current parameters of thefirst vehicle based on (i) the resultant parameters, and (ii) a receivedresponse from the first user with regards to the parameterrecommendations.
 2. The system of claim 1, wherein the transceiver isconfigured to receive first ones of the plurality of normalizedparameters from the mobile device and second ones of the plurality ofnormalized parameters from the server.
 3. The system of claim 1, whereinthe transceiver is configured to receive some of the plurality ofnormalized parameters from one or more vehicles other than the firstvehicle, the one or more vehicles including the second vehicle.
 4. Thesystem of claim 1, wherein the processing module is configured toreceive the plurality of normalized parameters from the portable memorydevice.
 5. The system of claim 1, wherein at least some of the pluralityof normalized parameters are specific to the first vehicle.
 6. Thesystem of claim 1, wherein: the transceiver is further configured toreceive second parameters from at least one of the server of thecloud-based network or one or more vehicles other than the firstvehicle, the one or more vehicles including the second vehicle; and theprocessing module is configured to generate the resultant parametersbased on the second parameters.
 7. The system of claim 1, wherein atleast some of the plurality of normalized parameters are parameters forthe first user and the first vehicle previously stored based on settingsestablished when the first user previously operated the first vehicle.8. The system of claim 1, wherein the plurality of normalized parametersinclude parameters set for the first user and the second vehicle or athird vehicle.
 9. The system of claim 8, wherein the plurality ofnormalized parameters do not include parameters set for the first userand the first vehicle.
 10. The system of claim 1, wherein the processingmodule is configured to: reading controller area network frames from acontroller area network bus; determining which particular vehicle codesare (i) available, (ii) being used by a particular year, make, model,and trim level of the first vehicle, and (iii) are adjustable;determining status values corresponding to the particular vehicle codesbased on the controller area network frames; and based on the particularvehicle codes and the status values, translate the plurality ofnormalized parameters to the resultant parameters.
 11. The system ofclaim 10, wherein the particular vehicle codes are for seat angles andlumbar pressures.
 12. The system of claim 10, wherein the particularvehicle codes are for passenger temperatures, driver temperatures, fanspeeds, and steering wheel temperature.
 13. The system of claim 10,wherein the particular vehicle codes are for radio channels and radiovolume levels.
 14. The system of claim 1, wherein the processing moduleis configured to, while generating the parameter recommendations:determine if the first user is a first time user of the parametertranslation services; determine if the first user is operating the firstvehicle for a first time; and based on the first user being the firsttime user of the parameter translation services or the first user usingthe first vehicle for a first time, generating the parameterrecommendations based on (i) parameters set in the first vehicle for oneor more users other than the first user, and (ii) parameters set for thefirst user in one or more vehicles other than the first vehicle, the oneor more users including the second user, and the one or more vehiclesincluding the second vehicle.
 15. The system of claim 1, wherein: theprocessing module is configured to, when providing the parametertranslation services, determine similarity scores to determine arecommended set of parameters to recommend to the first user; thesimilarity scores are generated based on similarities between a profileof the plurality of normalized parameters of the first user and one ormore profiles of normalized parameters of one or more other users, theone or more other users including the second user; the profile of theplurality of normalized parameters of the first user includes parametersof the first vehicle or one or more other vehicles, the one or moreother vehicles including the second vehicle; and the one or moreprofiles of the normalized parameters of the one or more other usersinclude parameters for the first vehicle or the one or more othervehicles.
 16. The system of claim 1, wherein: the processing module isconfigured to, determine a probability of parameters to determine a setof parameters to recommend to the first user; and the probability ofparameters is generated based on one or more averages of correspondingparameters set for (i) a plurality of users, and (ii) the first vehicleor one or more other vehicles, the plurality of users including thesecond user.
 17. The system of claim 1, wherein normalized parametersare parameters converted to values between 0 and 1 or between −1 and 1.18. The system of claim 1, wherein: the processing module is configuredto, when the first user is authorized to utilize the parametertranslation services, translate a user profile of normalized parametersfor the second vehicle or a third vehicle to a user profile of theplurality of normalized parameters for the first vehicle; and theresultant parameters are particular to the first vehicle.
 19. The systemof claim 1, wherein: each of the plurality of normalized parameters is auser adjustable setting of the first vehicle; and the plurality ofnormalized parameters include at least one of a door locking andunlocking policy, a lighting parameter, a vehicle-to-infrastructureparameter, a security parameter, or a dashboard parameter.
 20. Thesystem of claim 1, wherein: each of the plurality of normalizedparameters is a user adjustable setting of the first vehicle; and theplurality of normalized parameters include a door locking and unlockingpolicy, a lighting parameter, a vehicle-to-infrastructure parameter, asecurity parameter, and a dashboard parameter.
 21. The system of claim1, wherein the processing module is configured to: determine whether thefirst user is authenticated and authorized to access and operate thefirst vehicle based on at least one of a first digital key, a firstpassword or a first signature; and determine whether the first user isauthorized to utilize parameter translation services based on at leastone of a second digital key, a second password or a second signature.22. The system of claim 21, wherein the processing module is configuredto, based on the first user being authorized for the parametertranslation services and subsequent to the first user being permittedaccess to the interior of the first vehicle, translate the plurality ofnormalized parameters to the resultant parameters.
 23. A method ofsetting parameters within a first vehicle for a first user of the firstvehicle, the method comprising: storing in one or more memories aplurality of normalized parameters, wherein normalized parameters referto parameters that have been converted to values within a predeterminedrange for application to a plurality of different vehicle types, whereinthe plurality of normalized parameters are specific to the first user,and wherein each of the plurality of normalized parameters is aparameter of the first vehicle; receiving at least some of the pluralityof normalized parameters from at least one of a mobile device of thefirst user, a server in a cloud-based network, or a portable memorydevice; determining, based on credential information, whether the firstuser is authenticated and authorized to access and operate the firstvehicle, and (ii) whether the first user is authorized to utilizeparameter translation services, wherein determining whether the firstuser is authorized to utilize parameter translation services isperformed separate from determining whether the first user isauthenticated and authorized to access and operate the first vehicle;based on the first user being authenticated and authorized to access andoperate the first vehicle, permitting access to an interior of the firstvehicle; based on the first user being authorized for the parametertranslation services, translating the plurality of normalized parametersto resultant parameters based on a profile of parameters of the firstvehicle or a second vehicle, and the profile of parameters is specificto a second user; generating parameter recommendations based on theresultant parameters; presenting the parameter recommendations to thefirst user; and adjusting current parameters of the first vehicle basedon (i) the resultant parameters, and (ii) a received response from thefirst user with regards to the parameter recommendations.
 24. The methodof claim 23, wherein: first ones of the plurality of normalizedparameters are received from the mobile device; second ones of theplurality of normalized parameters are received from the server; andthird ones of the plurality of normalized parameters are received fromone or more vehicles other than the first vehicle.
 25. The method ofclaim 23, further comprising receiving second parameters from at leastone of the server of the cloud-based network or one or more vehiclesother than the first vehicle, wherein the resultant parameters aregenerated based on the second parameters.
 26. The method of claim 23,wherein at least some of the plurality of normalized parameters areparameters set for the first user and the first vehicle previouslystored based on settings established when the first user previouslyoperated the first vehicle; the plurality of normalized parametersinclude parameters set for the first user and the second vehicle; andthe plurality of normalized parameters do not include parameters set forthe first user and the first vehicle.
 27. The method of claim 23,further comprising: reading controller area network frames from acontroller area network bus; determining which vehicle codes areavailable and corresponding status values based on the controller areanetwork frames; and based on the vehicle codes and the status values,translating the plurality of normalized parameters to the resultantparameters.
 28. The method of claim 23, further comprising, whilegenerating the parameter recommendations: determining if the first useris a first time user of the parameter translation services; determiningif the first user is operating the first vehicle for a first time; andbased on the first user is the first time user of the parametertranslation services or the first user is using the first vehicle for afirst time, generating the recommendations based on (i) parameters setin the first vehicle for one or more users other than the first user,and (ii) parameters set for the first user in one or more vehicles otherthan the first vehicle, the one or more users including the second user,and the one or more vehicles including the second vehicle.
 29. Themethod of claim 23, further comprising determining similarity scores todetermine a recommended set of parameters to recommend to the firstuser, wherein: the similarity scores are generated based on similaritiesbetween a profile of parameters of the first user and one or moreprofiles of parameters of one or more other users, the one or more otherusers including the second user; the profile of parameters of the firstuser includes parameters of the first vehicle or one or more othervehicles, the one or more vehicles including the second vehicle; and theone or more profiles of parameters of the one or more other usersinclude parameters for the first vehicle or the one or more othervehicles.